For each eligible device or station the Validate Data command resolves to, the system will validate all open records in the date/time range specified by the command parameters, according to the validation functionality set up in your CygNet Measurement system.
Note: In the validation process, previously closed records within the specified time range are detected and ignored, and noted in the command log.
See FMS Commands and Validate Data for more information about this command.
See Scheduling FMS Command Tasks in the MSS for more information about scheduling commands.
See FMS ActiveX Controls and CxHmiFms for more information about using commands via FMS ActiveX controls on CygNet Studio or CygNet Vision screens.
See CxFms for more information about scripting commands.
To Configure a Validate Data Command
The following command definition properties apply to Validate Data commands.
| Property | Description |
|---|---|
|
Name |
Type in a Name for the new command. |
|
Command type |
Select the desired Command type from the drop-down menu. See FMS Commands for more information about available command types. |
|
Priority |
Select a processing queue Priority for the command from the drop-down menu. Options from least to greatest priority are as follows.
Default value is Low level processing queue priority. |
|
Logging |
Select a Logging level for the command results from the drop-down menu. Options are as follows.
Default value is Low level logging when scheduling a command in the MSS. Default value is High level logging when creating or running an ad-hoc command in FMS Explorer. |
|
Prompt when command runs |
Click to select/clear the check box to Prompt when command runs. Selecting this option means you will receive a prompt asking if you want to modify the parameters before the command is executed. |
The following command parameters apply to Validate Data commands when creating or editing commands via FMS Explorer.
| Description | Value |
|---|---|
|
Date format |
Select the desired date format from the drop-down menu. Options are as follows.
Default value is Device time. Notes: This parameter determines how the time window is selected in the database; not how the data is exported. For daily devices only, specifying start and end times of midnight (00:00:00) will always be interpreted as Contract time format, regardless of this selected parameter value. |
|
Start date/time |
The beginning of the time range for which to request data Click ... to access the Select Date and Time dialog box. See Selecting Date and Time for more information. See Note below this table. This parameter is required. |
|
End date/time |
The end of the time range for which to request data Click ... to access the Select Date and Time dialog box. See Selecting Date and Time for more information. See Note below this table. This parameter is required. |
Note: When using relative (rather than absolute) date/time, if both the start and end date/time have hour, minute, and second values of 00 (or if both are set to midnight), an additional day will be added to the date at the end of the range. This occurs because the service assumes the start of the day for the starting date/time and the end of the day for the ending date/time in these circumstances. Therefore requesting a time range from T to T will yield one day of data, and from T-1 to T will yield two days of data. If only one day of data is desired when using relative date/time, the start and end date/times must therefore be the same. If any of the start or end date/time hour, minute, or second values are specified as a value other than zero (or midnight) however, the range will be used as specified.
See Managing Node Commands for information about editing or deleting this command.
Note: Requests can only be processed for dates occurring after the device installation date(s). Compare the device installation date(s) to the command Start and End dates before running a Validate Data command.
See Running Node Commands for information about running this command.
|
|
|
